Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Python script for generating resource entries #440

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

allejo
Copy link
Contributor

@allejo allejo commented Feb 24, 2025

Since I've only committed the Python script portion of this PR, I'll mark this as a draft for now. As I was planning this out and writing it, I ran into some things I wanted to get more opinions on.

Should we download assets?

Downloading assets will fail if said files are not public. Some ideas on how to handle this situation:

  1. Auto-respond to the issue and request that the file be made public
  2. Use a service account to download files

Security Concerns

Automatically downloading files from the internet is a very secure thing to do. How should we handle the situation?

  1. Only download assets from a list of trusted GitHub usernames?
  2. Don't make this into an action and leave it as a manual script to run

/cc @machikoyasuda @thekaveman

Closes #435

Copy link

netlify bot commented Feb 24, 2025

Deploy Preview for cal-itp-website ready!

Name Link
🔨 Latest commit bd9c467
🔍 Latest deploy log https://app.netlify.com/sites/cal-itp-website/deploys/67bc5abc5f9e3400089f277e
😎 Deploy Preview https://deploy-preview-440--cal-itp-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@thekaveman
Copy link
Member

thekaveman commented Feb 24, 2025

@allejo hmm good point, we probably don't want to be downloading files from anywhere 😬

I don't think this new process is meant to fully replace the current workflow, just shortcut it a bunch and provide some early feedback for requestors (e.g. the preview link).

Given that, maybe we just use the asset link as provided in the issue, as a first pass. An engineer still needs to review (and possibly update) the PR anyway. We can try this out a few times and see how we like it or what changes to make. Can always come back to update this process further.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Exploration: From issue template to branches
2 participants